Skip to content

Expose read-only runtime discovery for consumers - #5

Open
graywolf336 wants to merge 1 commit into
releasefrom
feat/public-runtime-discovery
Open

graywolf336 wants to merge 1 commit into
releasefrom
feat/public-runtime-discovery

Conversation

@graywolf336

Copy link
Copy Markdown
Contributor

Expose the existing resolveRuntime function at the public entry point so Sherpa can discover missing Atomic installations in Git-only workspaces without native loading or CLI execution. No resolver, protobuf, fingerprint, or native contract changes. Document the metadata-only boundary versus full first-operation validation. TypeScript build and public-entry smoke passed; 30 existing tests passed. Twenty native integration tests rejected the host's installed Atomic 0.20.0 contract, as expected for this v0.22.0 consumer; matching-runtime verification will be recorded separately.

@graywolf336

Copy link
Copy Markdown
Contributor Author

Matching-contract native verification now passed using the existing Atomic 0.22.1 archive (its full embedded protobuf descriptor matches this consumer's pinned v0.22.0 fingerprint): 25 tests passed across bridge, status, vault, and public loading suites, including worker threads, repository isolation, native mutations/queries, and retry/cache behavior. The earlier 0.20.0 rejection was an environment mismatch, not a regression. TypeScript build, the 27 independent runtime/build tests, and the public metadata-only discovery smoke also passed. Sherpa vendors commit ec31722 for its fresh-workspace onboarding fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant